I'm a new DOORS Admin. I'm not only a new admin but I'm new to DOORS in general. A user submitted a request that I lock down the Object Text attribute on 2 modules to prevent further changes to the requirement. I successfully changed the first module (no problem) but when I got to the second module I find I don't have permissions. I logged in as Administrator and I still don't have permissions. How can it be that Administrator doesn't have permissions? Looking more closely in the attributes access permissions I see the text "This attribute definition is portioned in with access R." I looked up partitioning and learned something new. However, when I look at the Projects above this module, I see no defined partitions. Is there a way to reset the permissions to this module as such that the Administrator account has permissions to these attributes? felix@draper.com - Fri Feb 28 10:33:50 EST 2014 |
Re: Accessing attribute permissions There is a way to "remove" the "partition" feature of stuff with DXL (the "partition mask") but I'm confident it is a disaster to attempt to do so unless you figure to erase EVERY shred of "partition" of every single thing in the entire Project; as well as delete any Partitions. I would never go there unless I got advise from Mr MM about that. Serious comprehensive advise. Yes, the Administrator is disallowed from modifying Partition read-only data. In this case, I'd investigate:
I've seen some strange things vis-a-vis "Triggers" defined in Projects that are now Folders; and would expect similar confusion for Partitions. Once you find your Partition Definition, then go ahead and figure out how to "return" it. -Louie |
Re: Accessing attribute permissions llandale - Fri Feb 28 13:48:07 EST 2014 There is a way to "remove" the "partition" feature of stuff with DXL (the "partition mask") but I'm confident it is a disaster to attempt to do so unless you figure to erase EVERY shred of "partition" of every single thing in the entire Project; as well as delete any Partitions. I would never go there unless I got advise from Mr MM about that. Serious comprehensive advise. Yes, the Administrator is disallowed from modifying Partition read-only data. In this case, I'd investigate:
I've seen some strange things vis-a-vis "Triggers" defined in Projects that are now Folders; and would expect similar confusion for Partitions. Once you find your Partition Definition, then go ahead and figure out how to "return" it. -Louie Mmmm. I think the following sequence would create quite a fiasco:
You would, I suppose, experience symptoms like the ones you have; but you would not be able to track it down. -Louie
|
Re: Accessing attribute permissions llandale - Fri Feb 28 13:48:07 EST 2014 There is a way to "remove" the "partition" feature of stuff with DXL (the "partition mask") but I'm confident it is a disaster to attempt to do so unless you figure to erase EVERY shred of "partition" of every single thing in the entire Project; as well as delete any Partitions. I would never go there unless I got advise from Mr MM about that. Serious comprehensive advise. Yes, the Administrator is disallowed from modifying Partition read-only data. In this case, I'd investigate:
I've seen some strange things vis-a-vis "Triggers" defined in Projects that are now Folders; and would expect similar confusion for Partitions. Once you find your Partition Definition, then go ahead and figure out how to "return" it. -Louie Hi Louie, Thank you for your feedback. 1. No folders in the project line, just a project within a project. Would have been nice if it was that easy. 2. Looked for partitions in both projects, none are defined. Is it possible this is a Partition from someone else that is editable but not reconfigurable? One of my acquaintances here thinks there's a Super Administrator that has higher permissions than Administrator. Do you know anything about that? He says the super administrator is the ID used to create the database. If I had those privileges I'd be able to change anything. Never heard about that nor read about it. Thanks again, - Felix |
Re: Accessing attribute permissions llandale - Fri Feb 28 13:59:11 EST 2014 Mmmm. I think the following sequence would create quite a fiasco:
You would, I suppose, experience symptoms like the ones you have; but you would not be able to track it down. -Louie
I'm trying to track down the lineage of this module now. Looks like it may have been created by an individual outside of our company back in 2004. Getting a bad vibe on the permissions. I thought about exporting and recreating it but I need to preserve the links. |
Re: Accessing attribute permissions felix@draper.com - Fri Feb 28 14:05:27 EST 2014 Hi Louie, Thank you for your feedback. 1. No folders in the project line, just a project within a project. Would have been nice if it was that easy. 2. Looked for partitions in both projects, none are defined. Is it possible this is a Partition from someone else that is editable but not reconfigurable? One of my acquaintances here thinks there's a Super Administrator that has higher permissions than Administrator. Do you know anything about that? He says the super administrator is the ID used to create the database. If I had those privileges I'd be able to change anything. Never heard about that nor read about it. Thanks again, - Felix There is no such "Super Administrator", the user named "Administrator" is top of the heap. The "Administrator" has an implied RMCDA Access Record to everything in the database, without the need to have it explicitely set. (in fact, it cannot be explicitely set) That is not the same as "The administrator can do anything"; for example the Administrator may not delete an object in a module opened Read. The CPS GUI prevents the Administrator from making changes ..err.. making admin changes to a Project's CPS; that makes sense but lets not go there. However, the Administrator running DXL code can do these things. It's easy to code the resriction:
Likewise the GUI checks and prevents even the Administrator from changing read-only partitions. I don't know if it also disallows DXL run by the Administrator but I'm sure that is ill-advised. As for you're problem. I'm stuck. Be sure you login as the "Administrator" when looking for the partitions; even if you cannot change anything, it seems unlikely somebody would code denial of Read-Access for the Administrator. Perhaps the Partition Def is hidden from you. If you "CaptureLinks.dxl" you can store link information about this module. Once copied, you could then "Link-By-Attribute" to recreate the links from the new module. However, I think you will remain stuck with this corrupted partition module; unless someone posts some "remove partiion masks" program which may then allow you to purge it. However, I'd never be able to sleep since if you have this module as a problem you probably have some Partition problem somewhere else. Maybe someone has written some kind of "find anything partition" script which may provide some insight. -Louie |